This topic was automatically generated from Slack. You can find the original thread here.
Hi!
We have been using the linkedin oauth integration and it has worked great. Recently we have started getting this response for publishing posts to linkedin
<h1>Bad Message 400</h1><pre>reason: Transfer-Encoding and Content-Length</pre>
Anyone know if this is some issue on our end, or something somewhere in pipedream?
Hi Just to clarify, is this issue happening only during authentication (OAuth), or is it occurring when calling a specific LinkedIn action (for example, when publishing a post)?
Yeah sorry, its only specifically when publishing a post, authentication/account connection seem to work just fine
Is it possible that the pipedream proxy is appending both of these headers to the reqeust before passing it to linkedin?
Hi Anton, thanks for confirming.
I’ll try to replicate the issue on my side by publishing a post using the same flow and will check whether the Pipedream proxy is appending any additional headers before forwarding the request to LinkedIn. I’ll keep you updated with what I find.
I ran some tests here creating a post on LinkedIn through the Demo app, and it worked normally. I wasn’t able to reproduce the error. Are you publishing the post via a workflow, MCP, or Connect?
Using connect
